Skip to main content

iPool Suite Commandline Options

This section is a fresh reference for the command-line options accepted by the current iPool Suite. It covers the four BidManager Python tools (Generator, Aggregator, Editor, Converter) together with the BidManager -ibd2ibdx legacy rule-file converter, and the iPool simulation engine. It also covers the iPool Suite converters for dynamic bid rule files (-ibd2ibdx), batch files (--convert-bat) and legacy databases (-updatedb -conv). Each tab groups the options by tool or by category and gives, for each option, the argument it expects and a plain-language description of what it does.

All options shown here are current — they exist and take effect against the running code. Options that no longer exist, that emit a "flag not recognised" warning, or that are kept solely as backward-compatibility no-ops have been left out on purpose so the reader can rely on every row below.

bidmanager-generator — build a WESM historical bid from RTDOE/RTDOR interval data​

Produces one <YYYYMMDD>_F.bidx file per day of interval data.

OptionDescriptionArgument
-tStart delivery date. Required.YYYYMMDD (e.g. 20260101)
-ndaysNumber of days to convert starting from -t (default: 1).Any whole number ≥ 1
-bdirOutput directory for the produced .bidx file(s).Directory path
-rtdoeRTDOE interval-data input directory.Directory path
-rtdorRTDOR interval-data input directory (also drives spinmax/spinres priorities from reserve bids).Directory path
-marketMarket identifier.WESM or AEMO
-srcdbSysWESM reference database used for unit / site / capacity lookups.Path to SysWESM*.db / .db
-defaults-csvDefaults.csv file that resolves the paths above (MetadataDB, DirSub, DirBid, RTDOE, RTDOR).Path to Defaults.csv
-verboseRestore chatty representative-price WARNING output on stderr.(No argument)

Auto-loading. When invoked without every path explicitly given, Generator resolves inputs and databases through a fallback chain: an explicit flag on this command line wins, otherwise it reads the file named by -defaults-csv, then the graphical app's own persisted Defaults.csv, then canonical install-relative paths, and finally hard-coded fallbacks.